Value consistency

Characteristic Name:	Value consistency
Dimension:	Consistency
Description:	Data values are consistent and do not provide conflicting or heterogeneous instances
Granularity:	Element
Implementation Type:	Rule-based approach
Characteristic Type:	Declarative

Verification Metric:

The number of inconsistent data values reported in an attribute per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
For critical data elements provide standard classifications (values lists) for data entry interfaces and restrict arbitrary values across the system	(1) Country, city are taken from a standard list. (2) Generally accepted industry classifications are used to analyse customers industry wise (Education, Banking & Finance, Medical, Manufacturing…….
When data elements are combined for specific identification/management/accounting purposes, standardise such combinations and use them across the system.	(1) Customer and sales order are combined for identification purposes (2) Costs of wastage are associated with individual orders they are incurred and managed.
Define data attributes in such a way that data values are atomic and hence consistency can be maintained for any form of aggregation or consolidation	Name is divided into first name Middle name and Last Name
Maintain consistency in using unit of measures across different tables and different data bases	Sales price is in $ in Sales table and Accounts receivable ledger

Validation Metric:

How mature is the creation and implementation of the DQ rules to maintain value consistency

These are examples of how the characteristic might occur in a database.

Example:	Source:
School admin: a student’s date of birth has the same value and format in the school register as that stored within the Student database.	N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.
For example, data are inconsistent when it is documented that a male patient has had a hysterectomy.	B. Cassidy, et al., “Practice Brief: Data Quality Management Model” in Journal of AHIMA, 1998, 69(6).
the name of the city and the postal code should be consistent. This can be enabled by entering just the postal code and ﬁlling in the name of the city systematically through the use of referential integrity with a postal code table	Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006.
the data values ST Louis and Saint Louis may both refer to the same city. However, the recordings are inconsistent, and thus at least one of them is inaccurate.	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
Domain Level: The data values persist from a particular data element of the data source to another data element in a second data source. Consistency can also reflect the regular use of standardized values, articularly in descriptive elements. Entity Level: The entity’s domains and domain values either persist intact or can be logically linked from one data source to another data source. Consistency can also reflect the regular use of standardized values particularly in descriptive domains.	B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation.
Determines the extent to which distinct data instances provide nonconflicting information about the same underlying data object. For example, the salary range for level 4 employees must be between $40,000 and $65,000.	G. GATLING, C. B., R. CHAMPLIN, H. STEFANI, G. WEIGEL 2007. Enterprise Information Management with SAP, Boston, Galileo Press Inc.
Data is consistent if it doesn’t convey heterogeneity, neither in contents nor in form – anti examples: Order.Payment. Type = ‘Check’; Order. Payment. CreditCard_Nr = 4252… (inconsistency in contents); Order.requested_by: ‘European Central Bank’;Order.delivered_to: ‘ECB’ (inconsistency in form,because in the first case the customer is identified by the full name, while in the second case the customer’s acronym is used).	KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published.
Consistency can be curiously simple or dangerously complex. In its most basic form, consistency refers to data values in one data set being consistent with values in another data set. Two data values drawn from separate data sets may be consistent with each other, yet both can be incorrect.	LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.
In its most basic form, consistency refers to data values in one data set being consistent with values in another data set. A strict definition of consistency specifies that two data values drawn from separate data sets must not conflict with each other, although consistency does not necessarily imply correctness.	LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation.
Consistency, in popular usage, means that two or more things do not conflict with one another. This usage extends reasonably well to data values, although a bit of added discipline is desired.	REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc.

Data access control

Characteristic Name:	Data access control
Dimension:	Availability and Accessability
Description:	The access to the data should be controlled to ensure it is secure against damage or unauthorised access.
Granularity:	Information object
Implementation Type:	Process-based approach
Characteristic Type:	Usage

Verification Metric:

The number of tasks failed or under performed due to lack of data access control

The number of complaints received due to lack of data access control

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Periodically evaluate the security needs considering the criticality of data (Value, confidentiality, privacy needs etc.) and accessibility requirements of data and then update the information security policy consistently.	(1) Employee salary is a confidential data and hence need security against unauthorised access. (2) Master data has a high economic value to the organisation and hence need security against unauthorised access and change
Continuously evaluate the risks threats and identify the vulnerabilities for data and update the information security policy	(1) The frequency of security assessment for data associated with online transactions was increased due to the high volume of online transactions.
Implementation of access controls for each critical information as prescribed by the information security policy.	(1) An Employee’s salary data can be viewed only by his or her superiors. (2) Master data can be created and updated only by the authorised executives. (3) Login credentials are required for system access
Data is stored in secured locations and appropriate backups are taken	(1) Databases are stored in a special server and backups are taken regularly (2) Documents are saved using a content management system in a file server
Restrict the accessibility of information using software based mechanism	(1) Data encryption (2) Firewalls
Restrict the accessibility of information using hardware based mechanism	(1) Security tokens

Validation Metric:

How mature is the process of ensuring data access control

These are examples of how the characteristic might occur in a database.

Example:	Source:
if the ofﬁcial version of the minutes of a meeting is ﬁled by the records manager and thus protected from change, the unauthorised version will not form part of the ofﬁcial record.	K. Smith, “Public Sector Records Management: A Practical Guide”, Ashgate, 2007.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
Is the information protected against loss or unauthorized access?	EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.
Data is appropriately protected from damage or abuse (including unauthorized access, use, or distribution).	PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a.
The extent to which information is protected from harm in the context of a particular activity.	STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.
Access to data can be restricted and hence kept secure.	WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.